Avoiding Non-Technical Sources of Software Maintenance Technical Debt
نویسندگان
چکیده
Much of the emphasis in identifying a software maintenance project’s technical debt involves analysis of the code to be maintained. Our recent analysis of the sources of software maintenance cost have identified the major sources of technical debt for non-developer maintenance organizations to originate from non-technical acquisition and development decisions and practices. As a way of identifying and avoiding these sources, we have developed an initial counterpart of the Technical Readiness Level framework, called the Software Maintenance Readiness Level (SMRL) framework. This paper summarizes the main non-technical sources of software maintenance technical debt, their root causes, a first-cut SMRL framework, and our early experiences in evaluating it. Keywords—Software life cycle; Life cycle costs; Software maintainability; Software evolution; Software technical debt, Software maintainability readiness level
منابع مشابه
A Flowchart for Rapid Technical Debt Management Decision Making
Technical debt is known as delaying certain software maintenance tasks during software development life cycle to meet development goals in a short run. Such compromise increases maintenance cost in a way like growing financial interest in later development of software life cycle. Despite all the negative impact induced by technical debt, enterprise architects have to leverage between incurring ...
متن کاملWhen, Why and for Whom do Practitioners Detect Technical Debt? An Experience Report
Code cloning is one of the most well-known codelevel technical debts. In this paper, I discuss when, why and for whom practitioners detect code clones based on my experience of industry/university collaboration. At first, I introduce five project instances based on my experience. Next, I identify elements of the context model of a software maintenance project. After that, I discuss the impact o...
متن کاملDoes Technical Debt Lead to the Rejection of Pull Requests?
Technical Debt is a term used to classify non-optimal solutions during software development. These solutions cause several maintenance problems and hence they should be avoided or at least documented. Although there are a considered number of studies that focus on the identification of Technical Debt, we focus on the identification of Technical Debt in pull requests. Specifically, we conduct an...
متن کاملDebt-Prone Bugs: Technical Debt in Software Maintenance
Fixing bugs is an important phase in software development and maintenance. In practice, the process of bug fixing may conflict with the release schedule. Such confliction leads to a trade-off between software quality and release schedule, which is known as the technical debt metaphor. In this article, we propose the concept of debt-prone bugs to model the technical debt in software maintenance....
متن کاملVisualizing and Managing Technical Debt in Agile Development: An Experience Report
This paper reports the experience of an architecture team of a software development department with 25 agile teams in supporting technical decisions regarding technical practices. The main motivation to use technical debt metaphor was its acknowledged potential in driving software development and maintenance decisions, especially those long term maintenance tradeoffs which are usually less visi...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 2016